Conversation
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
hiagolcm
requested review from
gabpaladino,
leo-prange-vtex and
vmourac-vtex
and removed request for
a team
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
hiagolcm
force-pushed
the
feat/change-shipping-options-comopnents-to-delivery-promise-components
branch
2 times, most recently
from
d817cf8 to
5cc30f0
Compare
hiagolcm
force-pushed
the
feat/change-shipping-options-comopnents-to-delivery-promise-components
branch
from
5cc30f0 to
76a145d
Compare
iago1501
left a comment
iago1501
left a comment
There was a problem hiding this comment.
Just this small change in versioning.
Another important point to align here is that we are going to remove shipping-option dependency once we complete the migration from the two clients regarding this app
Co-authored-by: Iago Espinoza <iago1501@gmail.com>
hiagolcm
deleted the
feat/change-shipping-options-comopnents-to-delivery-promise-components
branch
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
3 participants
What problem is this solving?
vtex.delivery-promise-componentsDeliveryPromiseProvider context.How to test it?
Workspace
Screenshots or example usage:
Describe alternatives you've considered, if any.
Related to / Depends on
How does this PR make you feel? 🔗
![](put .gif link here - can be found under "advanced" on giphy)